System information for changing a configuration

ABSTRACT

Apparatuses, methods, and systems are disclosed for transmitting and/or receiving system information for changing a configuration. One apparatus includes a receiver that: receives first system information for a first configuration; and receives second system information for a second configuration based on the first configuration. The second system information includes changes to the first configuration without repeating information common to the first and second configurations.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 15/464,073filed on Mar. 20, 2017, which is hereby incorporated by reference in itsentirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to system information forchanging a configuration.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Positive-Acknowledgment (“ACK”), BinaryPhase Shift Keying (“BPSK”), Clear Channel Assessment (“CCA”), CyclicPrefix (“CP”), Channel State Information (“CSI”), Common Search Space(“CSS”), Discrete Fourier Transform Spread (“DFTS”), Downlink ControlInformation (“DCI”), Downlink (“DL”), Downlink Pilot Time Slot(“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced MobileBroadband (“eMBB”), Evolved Node B (“eNB”), European TelecommunicationsStandards Institute (“ETSI”), Frame Based Equipment (“FBE”), FrequencyDivision Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”),Guard Period (“GP”), Hybrid Automatic Repeat Request (“HARQ”),Internet-of-Things (“IoT”), Licensed Assisted Access (“LAA”), Load BasedEquipment (“LBE”), Listen-Before-Talk (“LBT”), Long Term Evolution(“LTE”), Multiple Access (“MA”), Modulation Coding Scheme (“MCS”),Machine Type Communication (“MTC”), Multiple Input Multiple Output(“MIMO”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), Non-Orthogonal Multiple Access (“NOMA”), Orthogonal FrequencyDivision Multiplexing (“OFDM”), Primary Cell (“PCell”), PhysicalBroadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”),Physical Downlink Shared Channel (“PDSCH”), Pattern Division MultipleAccess (“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”),Physical Random Access Channel (“PRACH”), Physical Resource Block(“PRB”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Radio Resource Control (“RRC”), Random AccessProcedure (“RACH”), Random Access Response (“RAR”), Reference Signal(“RS”), Resource Spread Multiple Access (“RSMA”), Round Trip Time(“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”),Scheduling Request (“SR”), Single Carrier Frequency Division MultipleAccess (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink ControlInformation (“UCI”), User Entity/Equipment (Mobile Terminal) (“UE”),Uplink (“UL”), Universal Mobile Telecommunications System (“UMTS”),Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NAK”).ACK means that a TB is correctly received while NAK means a TB iserroneously received.

In certain wireless communications networks, some system information maybe transmitted and/or received more often than is necessary. In someconfigurations, indexes and/or identifiers may be transmitted in systeminformation and used by UEs to enable the UEs to avoid reacquisition ofalready stored system information.

In certain configurations, there may be a large number of indexes and/oridentifiers. For example, each system information block or collection ofsystem information blocks may include a large number of parameters. Agiven network may use particular values of each parameter to configurethe UEs in the network at a given point of time. An index and/oridentifier for each possible configuration of parameters may be verylarge. In certain configurations, UEs may store a configurationcorresponding to each index and/or identifier. This may take a largeamount of storage space for the UEs. Moreover, a large load may beplaced on a network transmitting each configuration corresponding toeach index and/or identifier and UEs may store a large number ofconfigurations taking up considerable storage space. In variousconfigurations, there may be a small number of indexes and/oridentifiers. In such configurations, there may be a limited number ofconfigurations available to UEs.

BRIEF SUMMARY

Apparatuses for receiving system information for changing aconfiguration are disclosed. Methods and systems also perform thefunctions of the apparatus. In one embodiment, the apparatus includes areceiver that: receives first system information for a firstconfiguration; and receives second system information for a secondconfiguration based on the first configuration. In various embodiments,the second system information includes changes to the firstconfiguration without repeating information common to the first andsecond configurations.

In one embodiment, the first system information includes a systeminformation block. In a further embodiment, the second systeminformation includes changes to parameter values of the systeminformation block. In certain embodiments, the second system informationincludes additional parameters to those in the system information block.In various embodiments, the second system information indicates that itis based on the first system information. In some embodiments, the firstsystem information, the second system information, or some combinationthereof is discarded after a predetermined period of time.

A method for receiving system information for changing a configuration,in one embodiment, includes receiving first system information for afirst configuration. In various embodiments, the method includesreceiving second system information for a second configuration based onthe first configuration. In certain embodiments, the second systeminformation includes changes to the first configuration withoutrepeating information common to the first and second configurations.

In one embodiment, an apparatus includes a transmitter that transmitsfirst system information for a first configuration. In certainembodiments, the first configuration includes multiple systeminformation blocks. In various embodiments, the transmitter transmitssecond system information indicating system information blocks of themultiple system information blocks that have a second configurationavailable to be transmitted. In some embodiments, the secondconfiguration is based on the first configuration and includes changesto the first configuration without repeating information common to thefirst and second configurations.

In one embodiment, the second system information includes a list ofsystem information blocks that are not included in the first systeminformation. In a further embodiment, the second system informationincludes scheduling information for system information blocks of thelist of system information blocks. In certain embodiments, the secondsystem information includes scheduling information for informationcorresponding to the second configuration of the indicated systeminformation blocks of the multiple system information blocks that havethe second configuration available to be transmitted. In variousembodiments, the second system information includes informationindicating whether the second configuration for the indicated systeminformation blocks of the multiple system information blocks isbroadcast by default, broadcast by demand, or some combination thereof.

In some embodiments, the transmitter transmits third system informationindicating the second configuration for the indicated system informationblocks of the multiple system information blocks. In one embodiment, thethird system information includes changes to parameter values of theindicated system information blocks of the multiple system informationblocks. In certain embodiments, the third system information includesadditional parameters to those of the indicated system informationblocks of the multiple system information blocks. In variousembodiments, the first system information, the second systeminformation, the third system information, or some combination thereofis discarded after a predetermined period of time. In some embodiments,the multiple system information blocks include a first systeminformation block of a first type and a second system information blockof the first type, and the first and second system information blocksare different from one another.

In one embodiment, the second system information includes schedulinginformation for system information blocks broadcast regularly, systeminformation blocks not broadcast regularly, system information blocksusing the first configuration without the second configuration, systeminformation blocks using the first configuration with the secondconfiguration, or some combination thereof. In certain embodiments, thesecond system information includes a two-bit indication for each systeminformation block indicating whether the respective system informationblock is broadcast regularly, not broadcast regularly, uses the firstconfiguration without the second configuration, or uses the firstconfiguration with the second configuration.

A method for transmitting system information for changing aconfiguration, in one embodiment, includes transmitting first systeminformation for a first configuration. In some embodiments, the firstconfiguration includes multiple system information blocks. In variousembodiments, the method includes transmitting second system informationindicating system information blocks of the multiple system informationblocks that have a second configuration available to be transmitted. Incertain embodiments, the second configuration is based on the firstconfiguration and includes changes to the first configuration withoutrepeating information common to the first and second configurations.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for transmitting and/or receiving systeminformation for changing a configuration;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for receiving system information for changinga configuration;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for transmitting system information forchanging a configuration;

FIG. 4 illustrates one embodiment of communications for systeminformation for changing a configuration;

FIG. 5 is a schematic flow chart diagram illustrating one embodiment ofa method for transmitting system information for changing aconfiguration;

FIG. 6 is a schematic flow chart diagram illustrating another embodimentof a method for transmitting system information for changing aconfiguration;

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa method for receiving system information for changing a configuration;and

FIG. 8 is a schematic flow chart diagram illustrating a furtherembodiment of a method for transmitting system information for changinga configuration.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 fortransmitting and/or receiving system information for changing aconfiguration. In one embodiment, the wireless communication system 100includes remote units 102 and base units 104. Even though a specificnumber of remote units 102 and base units 104 are depicted in FIG. 1,one of skill in the art will recognize that any number of remote units102 and base units 104 may be included in the wireless communicationsystem 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 102 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 102 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 102may communicate directly with one or more of the base units 104 via ULcommunication signals.

The base units 104 may be distributed over a geographic region. Incertain embodiments, a base unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, or by any otherterminology used in the art. The base units 104 are generally part of aradio access network that includes one or more controllers communicablycoupled to one or more corresponding base units 104. The radio accessnetwork is generally communicably coupled to one or more core networks,which may be coupled to other networks, like the Internet and publicswitched telephone networks, among other networks. These and otherelements of radio access and core networks are not illustrated but arewell known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with the LTE of the 3GPP protocol, wherein the base unit 104transmits using an OFDM modulation scheme on the DL and the remote units102 transmit on the UL using a SC-FDMA scheme or an OFDM scheme. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication protocol, for example,WiMAX, among other protocols. The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The base units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 104 transmit DL communication signalsto serve the remote units 102 in the time, frequency, and/or spatialdomain.

In one embodiment, a base unit 104 may first system information for afirst configuration to the remote unit 102. In some embodiments, thefirst configuration may include one system information block, while inother embodiments, the first configuration may include multipleinformation blocks. In certain embodiments, the base unit 104 maytransmit to the remote unit 102 second system information indicatingsystem information blocks of multiple system information blocks thathave a second configuration available to be transmitted. In variousembodiments, the second configuration is based on the firstconfiguration and includes changes to the first configuration withoutrepeating information common to the first and second configurations.Accordingly, a base unit 104 may be used for transmitting systeminformation for changing a configuration.

In another embodiment, a remote unit 102 may receive first systeminformation for a first configuration. The remote unit 102 may receivesecond system information for a second configuration based on the firstconfiguration. In some embodiments, the second system informationincludes changes to the first configuration without repeatinginformation common to the first and second configurations. Accordingly,a remote unit 102 may be used for receiving system information forchanging a configuration.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forreceiving system information for changing a configuration. The apparatus200 includes one embodiment of the remote unit 102. Furthermore, theremote unit 102 may include a processor 202, a memory 204, an inputdevice 206, a display 208, a transmitter 210, and a receiver 212. Insome embodiments, the input device 206 and the display 208 are combinedinto a single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 stores data relating to various configurations. In someembodiments, the memory 204 also stores program code and related data,such as an operating system or other controller algorithms operating onthe remote unit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thebase unit 104 and the receiver 212 is used to receive DL communicationsignals from the base unit 104. In various embodiments, the receiver 212may be used to receive first system information for a firstconfiguration (e.g., base configuration, multiple base configurations,etc.). In some embodiments, the receiver 212 may be used to receivesecond system information for a second configuration (e.g., deltaconfiguration, multiple delta configurations, etc.) based on the firstconfiguration. In certain embodiments, the second system informationincludes changes to the first configuration without repeatinginformation common to the first and second configurations. Although onlyone transmitter 210 and one receiver 212 are illustrated, the remoteunit 102 may have any suitable number of transmitters 210 and receivers212. The transmitter 210 and the receiver 212 may be any suitable typeof transmitters and receivers. In one embodiment, the transmitter 210and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used fortransmitting system information for changing a configuration. Theapparatus 300 includes one embodiment of the base unit 104. Furthermore,the base unit 104 may include a processor 302, a memory 304, an inputdevice 306, a display 308, a transmitter 310, and a receiver 312. As maybe appreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In various embodiments, the transmitter 310 is used to transmit firstsystem information for a first configuration to the remote unit 102. Insome embodiments, the first configuration includes multiple systeminformation blocks, while in other embodiments, the first configurationincludes one system information block. In some embodiments, thetransmitter 310 may be used to transmit second system information to theremote unit 102. In one embodiment, the second system informationindicates system information blocks of the multiple system informationblocks that have a second configuration available to be transmitted. Invarious embodiments, the second configuration is based on the firstconfiguration and includes changes to the first configuration withoutrepeating information common to the first and second configurations.Although only one transmitter 310 and one receiver 312 are illustrated,the base unit 104 may have any suitable number of transmitters 310 andreceivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

FIG. 4 illustrates one embodiment of communications 400 for systeminformation for changing a configuration. Specifically, communications400 between a UE 402 and a gNB 404 are illustrated. The communications400 may facilitate providing the UE 402 with various configurations.

In certain embodiments, the gNB 404 may transmit first systeminformation 406 to the UE 402. In one embodiment, the first systeminformation 406 includes one or more base configurations. Any systeminformation block may have one or more base configurations. In variousembodiments, there may be multiple base configurations for one systeminformation block. Each of the base configurations may includeparticular values for parameters of one system information block,accordingly, each of the base configurations differ from one anotherbecause even if the base configurations are for the same systeminformation block, the values assigned to at least some of theparameters will differ. In some embodiments, a base configuration may beidentified using the following syntax SIR_(type, index); where typerefers to the content of the SIB (e.g., SIB₂ has a type value of “2”),and index defines a particular configuration of SIB₂. In variousembodiments, a base configuration may have a universal scope and/orapplicability or it may apply only to a limited area like a trackingarea (“TA”), a radio access network (“RAN”) area, a paging area, and soforth. In certain embodiments, the UE 402 may acquire and store baseconfigurations corresponding to one or more different scopes. As usedherein, “scope” may refer to a geographical area which may be a trackingarea, a routing area, or a RAN area specifically designed for a purpose(e.g., a collection of cells, a RAN paging area etc.). In someembodiments, scope may be limited or universal meaning that theacquired/used or broadcasted base configuration indexes are valid in alimited area or in an entire geography like a public land mobile network(“PLMN”) area. Accordingly, when a UE 402 changes its scope, the UE 402may use only the base configurations corresponding to its new scope and,in certain embodiments, may retain the base configuration correspondingto its previous scope that can be used upon the UEs re-entry in theprevious scope at a later point in time.

As used herein, base configuration (“BC”) may refer to a configurationwith respect to a particular SIB. In one example, there may be 20 SIBsdefined. A first cell/network might broadcast only 18 of the 20 definedSIBs because of various features that the first cell/network does notsupport. Out of 18 broadcast SIBs, 10 SIBs (e.g., SIB₂ to SIB₁₁) may beprovided using a base configuration and the remaining 8 SIBs may betransmitted in full (e.g., either broadcast regularly or providedon-demand). For the 10 SIBs that have a base configuration, some SIBsmay have one base configuration (e.g., BC-a) while other SIBs may havemultiple base configurations (e.g., BC-a, BC-b, BC-c, etc.). Forexample, SIB₂ might use BC-a for SIB₂, while SIB₃ might use BC-b forSIB₃, and SIB₄ might use BC-a for SIB₄, and so forth. A secondcell/network might provide only 5 SIBs (e.g., SIB₁₀ to SIB₁₄) using abase configuration. In certain embodiments, a UE may request BCs of acurrent cell/network (e.g., the first cell/network) and/or a neighboringcell/network (e.g., the second cell/network).

In some embodiments, the UE 402 may store the first system information406 and use the first system information 406 for multiple differentcells/networks that are part of the same scope. For example, when the UE402 moves out of one cell/network into another cell/network, the UE 402may keep the first system information 406 stored. Moreover, the firstsystem information 406 may remain unchanged when the UE 402 movesbetween cells/networks.

In some embodiments, the gNB 404 may transmit additional systeminformation 408 (e.g., second system information, third systeminformation, etc.) to the UE 402. In certain embodiments, the firstsystem information 406 and/or the additional system information 408 maybe transmitted together. In various embodiments, the first systeminformation 406 and/or the additional system information 408 may beconsidered system information or first system information.

In certain embodiments, the additional system information 408 mayinclude system information (e.g., second or third system information)for a second configuration (e.g., delta configuration) based on thefirst configuration. In some embodiments, the second configurationincludes changes to the first configuration without repeatinginformation common to the first and second configurations. In variousembodiments, the second configuration may refer to one or more deltaconfigurations for one or more system information blocks. In oneembodiment, the term “Delta-SI” may refer to a parameter set in whichparameters have been assigned values different from the values assignedto a base configuration. The Delta-SI may include only the parameter setout of the base configuration that has parameters different from thebase configuration. In other words, the Delta-SI may be considerablysmaller in size than the base configuration because it only includesparameters for a delta configuration that are changed from the baseconfiguration. In some embodiments, a base configuration that is closestto a configuration that a current cell/network needs may be called a“referred base configuration.” In certain embodiments, a cell/networkmay choose a referred base configuration from a set of baseconfigurations for a given SIB and may signal a Delta-SI along with thereferred base configuration to the UEs in the cell/network. Accordingly,the UEs in the cell/network may use the configuration from the referredbase configuration except for the parameter set found in the Delta-SI.In various embodiments, upon leaving the cell/network, the UE 402 maydelete any Delta-SIs so that the configuration of the referred baseconfiguration remains the same as it was before the UE 402 entered thecell/network.

In some embodiments, there may be more than one base configuration for aparticular type of SIB. For example, for SIB₂, there may be two baseconfigurations, a′ and b′ denoted SIB_(2, a′) and SIB_(2, b′),respectively. In one embodiment, a particular cell/network may findSIB_(2, a′) to be the most suitable and may only need to change a few ofthe parameter values of SIB_(2, a′). In certain embodiments, Delta-SImay contain new values of an existing parameter of a particular SIB. Insome embodiments, Delta-SI may contain new parameters for a particularSIB. In various embodiments, Delta-SI may contain new values of anexisting parameter of a particular SIB and/or new parameters for theparticular SIB.

Changes made by a cell/network may be one of many different types. Forexample, the cell/network may change from using a fully transmitted SIB(e.g., an SIB transmitted with actually signaling values of allparameters required in the cell/network) to a particular baseconfiguration of the same SIB (e.g., type 1 change). A UE that receivesthis type 1 change may start using the new values corresponding to theparticular base configuration if it has this base configuration for thisSIB stored; otherwise, it may initiate acquisition of the SIB (e.g.,based on scheduling information using broadcast channel or using anon-demand system information request procedure). As another example, thecell/network may change from using a base configuration of an SIB tousing a fully transmitted SIB (e.g., type 2 change). As a furtherexample, the cell/network may change from using a first baseconfiguration of an SIB having a certain type to a second baseconfiguration of the same SIB (e.g., type 3 change). As an additionalexample, the cell/network may change from using a first Delta-SI for anSIB to using a second Delta-SI for the SIB (e.g., type 4 change) and forthis change the base configuration in which the second Delta-SI isapplied remains the same (e.g., the same base configuration in which thefirst Delta-SI was being applied).

Depending on whether the type of change is a type 1 change, a type 2change, a type 3 change, or a type 4 change, different combinations of avalue tag, minimum system information, and/or paging messages may beused. For example, for a type 1 change, the change may be indicated in apaging message directly. As another example, for a type 1 change, theminimum system information may indicate the change and the UE 402 maynotice the change with every minimum system information modificationperiod (e.g., every 80 ms, etc.). As a further example, for a type 2change, a paging message may indicate an SIB/system information changewithout carrying the content of the change. In such an example, the UE402 may acquire the changed SIB/system information starting from thereacquisition of minimum system information, then schedulinginformation, and then the SIB. As another example, a type 3 change maybe done like a type 1 change. Furthermore, as an additional example, atype 4 change may be done by either a type 1 or a type 2 change,depending on the volume of the change.

In one embodiment, the system information includes schedulinginformation for system information blocks broadcast regularly, systeminformation blocks not broadcast regularly, system information blocksusing the first configuration without the second configuration, systeminformation blocks using the first configuration with the secondconfiguration, or some combination thereof. In certain embodiments, thesecond system information includes a two-bit indication for each systeminformation block indicating whether the respective system informationblock is broadcast regularly, not broadcast regularly, uses the firstconfiguration without the second configuration, or uses the firstconfiguration with the second configuration. Further, the second systeminformation may indicate if the second configuration(s) for theircorresponding system information block(s) are broadcast regularly or notbroadcast regularly. For system information block(s) or for secondconfiguration(s) indicated as not broadcast regularly, the UE may needto request them on an on-demand basis (e.g., request them using a RACHprocedure). Two methods are applicable here; one, in which a UEtransmits a particular specified/configured preamble to signal theSIB(s) or SI(s) that it is requesting; second, in which the UE includesdetailed information about its required SIB(s) or SI(s) optionally withthe base configurations that it needs in a current cell/network or in adifferent cell/network within the geographical scope using a RACHmessage 3 (“msg3”). The detailed information could be a bitmap havingone bit for each of the SIB-type and the UE sets the bit(s)corresponding to the SIB-type(s) that it does not have stored. In oneparticular embodiment, the UE may request the exact base configurationsfor each SIB-type that it needs.

The UE 402 may discard (e.g., delete, remove, etc.) base configurationsin one of many different ways. For example, in one embodiment, baseconfigurations may not be discarded unless explicitly signaled by acell/network to discard one or more of the base configurations. Incertain embodiments, a cell/network may explicitly signal to discard aparticular base configuration, all base configurations of one SIB,and/or all base configurations of many SIBs. As another example, in someembodiments, every base configuration and/or SIB may have a built-inthree hour discard timer so that after three hours the respective baseconfiguration and/or SIB will be discarded. The three hour discard timemay begin running at a time that the base configuration and/or SIBconfiguration is received by the UE 402 or at a time that the baseconfiguration and/or SIB is transmitted from the gNB 404. As a furtherexample, in various embodiments, a cell/network may configure which baseconfigurations and/or SIBs are subject to a three hour discard, whichbase configurations and/or SIBs are not subject to a three hour discard,and/or when the three hour discard timer is started. As yet anotherexample, in certain embodiments, every base configuration and/or SIB maybe discarded every three hours. In certain embodiments, a UE 402 mayrequest that a cell/network provide any unavailable (or discarded) SIBsor system information on an as-needed (e.g., on-demand) basis.

FIG. 5 is a schematic flow chart diagram illustrating one embodiment ofa method 500 for transmitting system information for changing aconfiguration. In some embodiments, the method 500 is performed by anapparatus, such as the base unit 104. In certain embodiments, the method500 may be performed by a processor executing program code, for example,a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

The method 500 may include transmitting 502 minimum system information.In certain embodiments, the minimum system information may includeinformation indicating PBCH, portions of SIB₁ for using and/or accessinga cell/network, portions of SIB₂ for using and/or accessing acell/network, and so forth. The method 500 may also include transmitting504 a used base configuration of all SIBs that are transmitted using abase configuration. The method 500 may include transmitting 506 anindication of which base configuration SIBs have a delta configuration(e.g., “Delta-SIB”). The method 500 may also include transmitting 508 alist of SIBs that are transmitted in full without using a baseconfiguration (e.g., SIBs that are available on-demand by a remote unit102, “remaining SIBs”). The method 500 may include transmitting 510scheduling information for Delta-SI and for the list of SIBs that aretransmitted in full without using a base configuration. In someembodiments, Delta-SIBs may be carried as part of one or more Delta-SI.For example, in one embodiment, there may be system information carryingonly Delta-SIBs. In certain embodiments, most SIBs are carried in systeminformation (“SI”) messages and mapping of SIBs to SI messages isflexibly configurable by a scheduling information list included inminimum system information (e.g., second system information), withcertain restrictions for example: each SIB is contained only in a singleSI message, and at most once in that message; only SIBs having the samescheduling requirement (e.g., periodicity) may be mapped to the same SImessage etc. In certain embodiments, different SI messages may carry oneor more SIBs in full or in delta, the used base configuration of one ormore SIBs, or a combination thereof, where SI is transmitted accordingto the scheduling information. In various embodiments, a special SImessage may carry some or all Delta-SIB configurations.

FIG. 6 is a schematic flow chart diagram illustrating another embodimentof a method 600 for transmitting system information for changing aconfiguration. In some embodiments, the method 600 is performed by anapparatus, such as the base unit 104. In certain embodiments, the method600 may be performed by a processor executing program code, for example,a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

The method 600 may include transmitting 602 minimum system information.In certain embodiments, the minimum system information may includeinformation indicating PBCH, portions of SIB₁ for using and/or accessinga cell/network, portions of SIB₂ for using and/or accessing acell/network, and so forth. The method 600 may also include transmitting604 a list of SIBs that are transmitted. In one embodiment, a flag maybe transmitted with an SIB in the list indicating whether the SIB isalways transmitted or transmitted on-demand (e.g., when requested). Themethod 600 may include transmitting 606 scheduling information for thelist of SIBs. The method 600 may also include transmitting 608 a usedbase configuration of each SIB that is transmitted using a baseconfiguration. The method 600 may include transmitting 610 an indicationof which base configuration SIBs have a delta configuration (e.g.,“Delta-SIB”). In certain embodiments, a system information message maycarry one or more SIBs. For example, in one embodiment, the systeminformation carries information for two SIBs, one that a Delta-SIB anduses a base configuration and another that is a full SIB.

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa method 700 for receiving system information for changing aconfiguration. In some embodiments, the method 700 is performed by anapparatus, such as the remote unit 102. In certain embodiments, themethod 700 may be performed by a processor executing program code, forexample, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

The method 700 may include receiving 702 first system information for afirst configuration. The method 700 also includes receiving 704 secondsystem information for a second configuration based on the firstconfiguration. In certain embodiments, the second system informationincludes changes to the first configuration without repeatinginformation common to the first and second configurations.

In one embodiment, the first system information includes a systeminformation block. In another embodiment, the first system informationmay include multiple system information blocks. In a further embodiment,the second system information includes changes to parameter values ofone or more system information blocks. In certain embodiments, thesecond system information includes additional parameters to those in thesystem information block. In various embodiments, the second systeminformation indicates that it is based on the first system information.In some embodiments, the first system information, the second systeminformation, or some combination thereof is discarded (e.g., deleted)after a predetermined period of time.

FIG. 8 is a schematic flow chart diagram illustrating a furtherembodiment of a method 800 for transmitting system information forchanging a configuration. In some embodiments, the method 800 isperformed by an apparatus, such as the base unit 104. In certainembodiments, the method 800 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 800 may include transmitting 802 first system information fora first configuration for a remote unit 102. In some embodiments, thefirst configuration includes one or more system information blocks. Themethod 800 also includes transmitting 804 second system informationindicating system information blocks of one or more system informationblocks that have a second configuration available to be transmitted. Invarious embodiments, the second configuration is based on the firstconfiguration and includes changes to the first configuration withoutrepeating information common to the first and second configurations.

In one embodiment, the second system information includes a list ofsystem information blocks that are not included in the first systeminformation. In a further embodiment, the second system informationincludes scheduling information for system information blocks of thelist of system information blocks. In certain embodiments, the secondsystem information includes scheduling information for informationcorresponding to the second configuration of the indicated systeminformation blocks of the one or more system information blocks thathave the second configuration available to be transmitted. In variousembodiments, the second system information includes informationindicating whether the second configuration for the indicated systeminformation blocks of the one or more system information blocks isbroadcast (e.g., transmitted) by default, broadcast by demand, or somecombination thereof.

In some embodiments, the transmitter transmits third system informationindicating the second configuration for the indicated system informationblocks of the one or more system information blocks. In one embodiment,the third system information includes changes to parameter values of theindicated system information blocks of the one or more systeminformation blocks. In certain embodiments, the third system informationincludes additional parameters to those of the indicated systeminformation blocks of the one or more system information blocks. Invarious embodiments, the first system information, the second systeminformation, the third system information, or some combination thereofis discarded after a predetermined period of time. In some embodiments,the one or more system information blocks include a first systeminformation block of a first type and a second system information blockof the first type, and the first and second system information blocksare different from one another.

In one embodiment, the second system information includes schedulinginformation for system information blocks broadcast regularly, systeminformation blocks not broadcast regularly, system information blocksusing the first configuration without the second configuration, systeminformation blocks using the first configuration with the secondconfiguration, or some combination thereof. In certain embodiments, thesecond system information includes a two-bit indication for each systeminformation block indicating whether the respective system informationblock is broadcast regularly, not broadcast regularly, uses the firstconfiguration without the second configuration, or uses the firstconfiguration with the second configuration.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method comprising: receiving a system information block; inresponse to receiving the system information block, starting a timercorresponding to the system information block; and discarding the systeminformation block a predetermined time after the timer is started. 2.The method of claim 1, wherein receiving the system information blockcomprises receiving a plurality of system information blocks.
 3. Themethod of claim 2, further comprising, in response to receiving theplurality of system information blocks, starting a corresponding timercorresponding to each system information block of the plurality ofsystem information blocks.
 4. The method of claim 3, further comprisingdiscarding each system information block of the plurality of systeminformation blocks the predetermined time after the corresponding timeris started.
 5. The method of claim 1, wherein the predetermined timecomprises three hours.
 6. The method of claim 1, wherein discarding thesystem information block comprises deleting the system informationblock.
 7. The method of claim 1, wherein a validity of the systeminformation block is based on a radio access network area inside of apublic land mobile network area corresponding to the system informationblock.
 8. An apparatus comprising: a receiver that receives a systeminformation block; and a processor that: in response to receiving thesystem information block, starts a timer corresponding to the systeminformation block; and discards the system information block apredetermined time after the timer is started.
 9. The apparatus of claim8, wherein the receiver receiving the system information block comprisesthe receiver receiving a plurality of system information blocks.
 10. Theapparatus of claim 9, wherein the processor, in response to receivingthe plurality of system information blocks, starts a corresponding timercorresponding to each system information block of the plurality ofsystem information blocks.
 11. The apparatus of claim 10, wherein theprocessor discards each system information block of the plurality ofsystem information blocks the predetermined time after the correspondingtimer is started.
 12. The apparatus of claim 8, wherein thepredetermined time comprises three hours.
 13. The apparatus of claim 8,wherein the processor discarding the system information block comprisesthe processor deleting the system information block.
 14. The apparatusof claim 8, wherein a validity of the system information block is basedon a radio access network area inside of a public land mobile networkarea corresponding to the system information block.